home *** CD-ROM | disk | FTP | other *** search
- Path: druid.borland.com!usenet
- From: pete@borland.com (Pete Becker)
- Newsgroups: comp.lang.c++
- Subject: Re: Coding Standards
- Date: 22 Mar 1996 19:14:28 GMT
- Organization: Borland International
- Message-ID: <4iuu6k$6a6@druid.borland.com>
- References: <4hj8ek$elu@sam.inforamp.net> <4hktar$5o2@galaxy.ucr.edu> <4hmqol$97j@abacus.abasoft.co.uk> <4hsg8r$pmm@sam.inforamp.net> <4i9o6j$p4l@daisy.pgh.wec.com> <4idskb$pc1@sam.inforamp.net> <314EBD08.43BC@virtus.com> <4io2i7$n9v@sam.inforamp.net>
- NNTP-Posting-Host: pbecker.borland.com
- Mime-Version: 1.0
- Content-Type: Text/Plain; charset=ISO-8859-1
- X-Newsreader: WinVN 0.99.5
-
- In article <4io2i7$n9v@sam.inforamp.net>, rmorin@inforamp.net says...
- >
- >In article <314EBD08.43BC@virtus.com>,
- > "Richard F. Albury" <richard.albury@virtus.com> wrote:
- >>// is the standard C++ comment, so I'm not sure I understand your objection.
- >
- >What I meant was that the /* */ has been the only standard comment for years.
- > The // comment style is a new proposed standard.
- >
- >>> -a class which can be instantiated with a "new" must have a copy
- >>> constructor, a destructor and an assignment operator definition.
- >>
- >>It's good discipline. Read Scott Meyers' books for more info.
- >
- >Unfortunately, if we follow everybodies good discipline guidelines, we would
- >miss our October deadline by a few years.
- >
-
- Unfortunately, if you don't follow guidelines like this, you will miss your
- subsequent maintenance deadlines by many years. You'll spend all your time
- tracking down mysterious failures that arise when you try to enhance the
- program, rather than spending time on the enhancements themselves.
-
-